Method for routing ad-hoc signals

ABSTRACT

An ad-hoc network is a typically a dynamic collection of nodes capable of communicating therebetween without the aid of pre-established infrastructure. Ad-hoc networks differ from traditional networks in that the topology of interconnections between nodes is inherently dynamic and not fixed. Generally, the routing protocols belong to two groups: proactive and reactive. Proactive protocols attempt to maintain correct and up-to-date routing information at every node. Reactive protocols, in turn, collect necessary routing information only if a pair of nodes are to establish a communication. In accordance with embodiments of the invention a reactive ad-hoc network protocol is disclosed that uses controlled flooding to broadcast packets of information within the ad-hoc network. Furthermore, the ad-hoc network protocol does not maintain up-to-date routing information at every node in an ad-hoc network and does not utilize specific control messages to assure that packets within the ad-hoc network follow optimal paths.

This application claims priority as a Continuation-in-Part of U.S.patent application Ser. No. 10/372,167 filed Feb. 25, 2003 entitled“Method for Routing Ad-Hoc Signals”, which itself claims priority fromU.S. Provisional Application Ser. No. 60/358,703 filed Feb. 25, 2002entitled “Method for Routing Ad-Hoc Signals.”

FIELD OF THE INVENTION

This invention relates to data communication networks and morespecifically to a method of routing messages using an ad-hoc datacommunication network having flexible network topology.

BACKGROUND OF THE INVENTION

An ad-hoc network is a typically a dynamic collection of nodes capableof communicating therebetween without the aid of pre-establishedinfrastructure. Ad-hoc networks differ from traditional networks in thatthe topology of interconnections between nodes is inherently dynamic andnot fixed. Consequently, ad-hoc networks do not rely on a centralizedauthority in order to coordinate the communication between the nodes.

A number of routing protocols used to implement ad-hoc networks havebeen presented in the literature. Generally, the routing protocolsbelong to two groups: proactive and reactive. Proactive protocolsattempt to maintain correct and up-to-date routing information at everynode. This information is then used to establish connections between thenodes that wish to communicate. Reactive protocols, in turn, collectnecessary routing information only if a pair of nodes are to establish acommunication.

Many existing ad-hoc network protocols are rather complex, which seemsto be one of the reasons why ad-hoc devices utilizing ad-hoc protocolsare not widely available. Considering a highly dynamic nature of ad-hocnetworks, that frequent change in their topology, it is the opinion ofthose of skill in the art that reactive protocols are more suitable foruse in this environment. Furthermore, overhead associated withmaintaining up-to-date routing information at every node in an ad-hocnetwork is known to be expensive.

The dynamic environment of ad-hoc networks calls for new routingprotocols to be implemented, since the traditional routing protocols arenot current with frequent topology changes that occur in ad-hocnetworks.

OBJECT OF THE INVENTION

It is an object of this invention to provide a method of routing signaldata using a wireless ad-hoc network in which network topology changesare frequent

SUMMARY OF THE INVENTION

In accordance with an embodiment of the present invention, there isprovided a method of providing a reactive ad-hoc network comprising thesteps of:

(a) providing at least a source node, a first node, a second other node,and a destination node of a plurality of nodes, each node comprising atleast a processor, a memory, and a transceiver in communication with theprocessor for receiving data and transmitting data via a wirelesscommunication medium;(b) providing a packet of data comprising message data and header datato the processor of the first node for transmission therefrom, theheader data comprising data relating to the source node and thedestination node for the packet of data, data relating to a number ofhops already completed for the packet of data, data relating to mobilityof packets of data within the reactive ad-hoc network transmitted fromthe source node to the destination node and the destination node to thesource node, data relating to a number of hops between the source nodeand the destination node for a previous packet of data, and a uniqueidentifier for the packet of data;(c) transmitting the data from the transceiver of the first node in abroadcast fashion;(d) receiving the data at the transceiver of the second other node;(e) calculating at the second other node a discard counter, the discardcounter determined in dependence upon at least the direction of thepacket relative to the source node and destination node, a packetmobility factor in the direction of the packet, the number of hops fromthe source node to the second other node, the number of hops from thedestination node to the second other node and the number of hops betweenthe source node and destination node for a previous packet of data;(f) determining whether to discard the packet in dependence upon atleast the discard counter; and(g) discarding the packet and decrementing the discard counter where thedetermination is made to discard.

In accordance with another embodiment of the invention there is provideda method of providing a reactive ad-hoc network comprising the steps of:

(a) providing at least a first node, a second other node, a source nodeand a destination node of a plurality of nodes, each node comprising atleast a processor, a memory, and a transceiver in communication with theprocessor for receiving data and transmitting data via a wirelesscommunication medium;(b) providing packet of data comprising message data and header data tothe processor of the first node for transmission therefrom, the headerdata comprising data relating to the source node and the destinationnode for the packet of data, data relating to a number of hops alreadycompleted for the packet of data, data relating to mobility of packetsof data within the reactive ad-hoc network transmitted from the sourcenode to the destination node and the destination node to the sourcenode, data relating to a number of hops between the source node and thedestination node for a previous packet of data, and a unique identifierfor the packet of data;(c) transmitting the data from the transceiver of the first node to thetransceiver of the destination node without modification via the secondother node other than the first node or the destination node absent aknown available route; and(d) calculating at the second other node a discard counter, the discardcounter determined in dependence upon at least the direction of thepacket relative to the source node and destination node, a packetmobility factor in the direction of the packet, the number of hops fromthe source node to the second other node, the number of hops from thedestination node to the second other node and the number of hops betweenthe source node and destination node for a previous packet of data;(f) determining whether to discard the packet in dependence upon atleast the discard counter; and(g) discarding the packet and decrementing the discard counter where thedetermination is made to discard.

In accordance with another embodiment of the invention there is provideda node forming part of a reactive ad-hoc network comprising:

(a) a processor;

(b) a memory in communication with the processor;

(c) a transceiver in communication with the processor for receivingsignals and for transmitting signals, the signals transmitted andreceived via a wireless communication medium; and

(d) an application in execution upon the processor executing an ad-hoccommunications protocol to communicate with at least one other node toform an ad-hoc network, the application:

-   -   (i) at least one of generating, receiving from the transceiver        and providing to the transceiver a packet of data comprising        message data and header data, the header data comprising data        relating to a source node and a destination node for the packet        of data, data relating to a number of hops already completed for        the packet of data, data relating to mobility of packets of data        within the reactive ad-hoc network transmitted from the source        node to the destination node and the destination node to the        source node, data relating to a number of hops between the        source node and the destination node for a previous packet of        data, and a unique identifier for the packet of data;    -   (ii) calculating a discard counter, the discard counter being        determined in dependence upon at least the direction of a        received packet relative to the source node and destination        node, a packet mobility factor in the direction of the packet,        the number of hops from the source node to the second other        node, the number of hops from the destination node to the second        other node and the number of hops between the source node and        destination node for a previous packet of data; and    -   (iii) determining whether to discard the packet in dependence        upon at least the discard counter and discarding the packet and        decrementing the discard counter where the determination is made        to discard.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments of the invention will now be described inconjunction with the following drawings, in which:

FIG. 1 is a simplified diagram of an ad-hoc network;

FIG. 2 illustrates a simplified diagram of an application layer, atransport layer, a Network Layer 203, including the TARP, and a datalink layer 204, in accordance with an embodiment of the invention;

FIG. 3A illustrates a Duplicate Discard (DD) process steps;

FIG. 3B illustrates a Sub-optimal Path Discard (SPD) process steps;

FIG. 4 illustrates a node in the AHN having memory therein for storingof cache data;

FIG. 5A illustrates a flowchart of the PacketTransmission process;

FIG. 5B illustrates a flowchart of the PacketTransmissionResult process;

FIG. 5C illustrates a flowchart for the PacketFwdRcv process;

FIG. 5D illustrates a flowchart for the PacketFwdRcvResult process;

FIG. 5E illustrates a flowchart for the CacheTimer process;

FIG. 6A illustrates a flowchart for the dupDiscardAlg function;

FIG. 6B illustrates a flowchart for the getTransmissionTime function;

FIG. 6C illustrates a flowchart for the subPathDiscardAlg function;

FIG. 6D illustrates a flowchart for the deterministicDiscard function;

FIG. 6E illustrates a flowchart for the probabilisticDiscard function;

FIG. 6F illustrates a flowchart for the avgTransmissionTime function;

FIG. 7 illustrates three nodes, S, D, and K, with node K disposedbetween nodes S and D;

FIG. 8 illustrates nodes S and D, having a first path that involvespropagation intermediate nodes K, L and M, and a second path thatinvolves propagation through a single intermediated node Z;

FIG. 9A illustrates a table showing SPD source cache entries for nodes Dand S for a packet p1 sent by D to S and arriving at node S;

FIG. 9B illustrates the SPD cache entries at nodes K, L, and M;

FIG. 9C illustrates a reverse of that shown in FIG. 9 a, where a packetp2 of a reverse communication session from S to D arrives at node D;

FIG. 9D illustrates the SPD cache entries at nodes K, L, and M, wherethe packet traveling from nodes S to D carries values of path h=2 andmobility factor m=1;

FIG. 9E illustrates further SPD cache entries at nodes K, L, and M wherea packet p3 is sent by nodes D to S for arrival at node S;

FIG. 9F illustrates the SPD cache at nodes K, L, and M, where a packetp4 of a reverse communication session from nods S to D arrives to nodeD;

FIG. 9G illustrates the SPD cache at nodes K, L, and M, where a packetp5 sent by node D to node S arrives at S;

FIG. 9H illustrates the SPD cache 401 at nodes K, L, and M, where aftertransmission of packet p6 from S to D, packet p7 from D to S, and packetp8 of a reverse communication session from S to D; and,

FIG. 10 illustrates an example where setting F(p) to its maximum valueof p=1 is potentially beneficial.

DETAILED DESCRIPTION

Typically, an ad-hoc network (AHN) offers the possibility to connectlarge numbers of communication devices, in the form of nodes, withoutsignificant infrastructure costs. Each node within the AHN has threefunctions. As is illustrated in FIG. 1, a node is either for being asource 101 of signal data transmitted through the AHN, a finaldestination 103 of signal data transmitted through the ad-hoc network,or a relay 102 for propagating signal data between two nodes. Throughad-hoc networks various types of signal data are transmittable from onenode to another node as long as the nodes are in transmission andreception range with each other. Node K 102 is intermediate to nodes Sand D, and therefore packets from nodes S to D, or D to S, arepreferably propagated through node K.

Ad-hoc networks are dynamic networks that support moving, removing andaddition of nodes therein. Typically, prior art AHNs require largebandwidth nodes to manage signals propagating between the nodes thereof.

Referring to FIG. 1, a simplified diagram of an ad-hoc network is shown.The network comprises a source node 101, a destination node 103 and anintermediary node 102. As is well known in the art, there may be anynumber of intermediary nodes. Each intermediary node is provided withwireless communication hardware for transmitting, receiving, andrelaying of data.

To overcome drawbacks, of prior art ad-hoc networks, the ad-hoc networkspreferably provide a method of preventing bottlenecks as a result ofsignal routing for use in directing relayed signals toward an intendeddestination. This is particularly useful in proactive ad-hoc networks.Unfortunately, these methods of implementing signal extinction are oftencumbersome and require significant processing power and systemresources.

The present invention as described herein with reference to particularembodiments thereof is in reference to a protocol, in the form of a tinyad-hoc routing protocol (TARP) for routing ad-hoc signals within thead-hoc network. Preferably, the embodiments of the invention allow fortransmitting and receiving of signals within the AHN with a limitedbandwidth. Further preferably, the protocol functions with the use of arelatively small capacity memory 104 disposed in each node for storingexecutable instructions for implementing of the protocol.

Referring to FIG. 2, a simplified diagram of an application layer 201, aTransport Layer 202, a Network Layer 203, including the TARP, and a datalink layer 204, in accordance with an embodiment of the invention, areshown. The TARP is described hereinbelow with the use of the followingfunctions, processes and processes.

The idea behind TARP is based on a process termed “controlled flooding.”When a node sends a packet, the packet broadcasts it to neighbouringnodes, where this approach is particularly natural is in wirelessnetworks where all received nodes are sufficiently close to atransmitter in order to receive the transmission.

A node receiving the packet determines from a destination field of thepacket whether it is an intended receiver of the packet and the nodereceives the packet. In the process of receiving the packet by the node,a payload of the packet is provided to the Transport Layer 202.

Otherwise, the node uses processes in accordance with embodiments of theinvention to limit a number of packets in the network. These processesare: a Duplicate Discard (DD) process and a Sub-optimal Path Discard(SPD) process, which are described hereinbelow.

In execution of the DD process, as illustrated in FIG. 3A, a node checksthe packet in order to determine if it has already processed the packet.If the answer is no, the packet is rebroadcast from this node,otherwise, the received packet is a copy of an original packet. Theoriginal packet has propagated through this node using a possiblyshorter path. Thus, the packet is discarded since there is little pointin forwarding the same packet over the previously used path.

In the SPD process, as illustrated in FIG. 3B, a node determines whetherit lies on the shortest path between a packet's source and destinationnodes, using predetermined fields in the packet's header. If the path isdeemed to be shortest, the packet is rebroadcast from this node.Otherwise, the packet is discarded. There is little point in forwardinga packet that has a high probability of being discarded by a destinationnode since it is a duplicate. Typically, this occurs when a copy of thatpacket arrived at a destination node faster after having propagatedusing a shorter path.

In order for a node to determine that the received packet is a duplicatein implementing of the DD process, the packet preferably stores certaininformation therein relating to its predecessor node. It is preferablefor the node to determine a sufficient timeout after which the packet isdeleted. If the packet is kept for too long in the node, the memoryrequirements for the potentially increase. If the packet is deleted tooearly, a packet's duplicate is potentially propagated in the AHN, thuspotentially wasting AHN bandwidth.

In implementing of the SPD process, a node discards packets sent by agiven source node once it has determined that it is not located on thesub-optimal path. At some point, however, the node resumes forwardingpackets. The SPD process thus dynamically determines a predeterminedamount of time for which packets are discarded.

Packet Format.

Each packet propagated in the AHN comprises fields listed hereinbelow.The Network Layer 203 header of every packet contains the followingfields: └ID, r, h, h, m. m_, where the packet id is determined from thefollowing ID=S, D, s, n, k, where:

S—source node of a packet;

D—destination node of a packet; if D=0, then the packet is broadcast;

s—identifier unique for a communication session from S to D;

n—sequential number of a packet sent by S to D during a communicationsession whose identifier is s;

k—transmission number of a packet identified by S, D, s and n thatallows the Network Layer 203 to distinguish retransmissions of the samepacket;

r—the maximum range of a packet expressed in hops, a packet is removedfrom the network when h=r

h—hop counter that measures the number of hops that a packet hastraveled so far (h=0 at a source);

h—the number of hops traveled by the last packet on the reverse pathfrom D to S;

m—mobility factor to be used by the SPD process for communicationsession from S to D;

m—mobility factor to be used by the SPD process by a reversecommunication session from D to S (both m and m are short—2, 3 bits)

The last four fields are used by Sub-optimal Path Discard (SPD) processthat discards packets relayed over a sub-optimal path. If D=0, thepacket is delivered to all destinations nodes that are no further than rhops away from source S. This provides the broadcasting capability tothe TARP. More on the SPD process is described hereinbelow.

Control Messages.

Control messages are exchanged between Transport Layer 202, NetworkLayer 203 and Data Link Layer 204. The purpose of these control messagesis to notify the protocols in execution within the Network Layer 203 andin the Transport Layer 202 about whether the transmission of a packet toa neighboring node was a success or not.

DLSuccTrans(ID) and DLFailTrans(ID) are control messages that arereceived by the Network Layer 203 (TARP) from the Data Link Layer 204,where: A DLSuccTrans(ID) message indicates that the Data Link Layer 204successfully sent a packet identified by ID. Thus, a neighboring nodereceived the packet. A packet is optionally successfully received byseveral neighboring nodes, where each of these events generates aseparate DLSuccTrans message. A DLFailTrans(ID) message indicates thatthe Data Link Layer 204 was unable to send a packet identified by ID.This message is generated when the Data Link Layer 204 generates a timeout signal waiting for an acknowledgement of packet receipt from anyneighboring node.

NLSuccTrans(ID) and NLFailTrans(ID) are messages that are provided fromthe Network Layer 203 (TARP) 203 to the Transport Layer 202, where: aNLSuccTrans(ID) message corresponds to the DLSuccTrans(ID) message andis triggered by the DLSuccTrans(ID) message. A NLFailTrans(ID) messagecorresponds to the DLFailTrans(ID) message and is triggered by theDLFailTrans(ID) message.

Timing Parameters.

Various timing parameters are used for implementing of the TARP and aredefined hereinbelow:

Δt_(t)—transmission time, the time between when a packet is provided tothe Data Link Layer and when the Data Link Layer returns a message thatindicates that the packet was received by a neighboring node;

Δt_(avg)—average transmission time of a packet;

t_(cur) the current time;

Δt_(r)—time for which an entry is kept in a DD cache;

t_(r)—time at which a DD cache entry is to be deleted, if an entry isdeleted at a current time t_(cur), the entry in the DD cache was made attime Δt_(r)—ΔT_(r);

Δt_(avg)—time for which an entry is kept in a transmission timeregister;

t_(b)—time at which an entry is made in a transmission time register

DD Cache.

In accordance with that illustrated in FIG. 4, a DD cache 403 is for useby the Duplicate Discard (DD) process. Nodes executing the TARP do notmaintain routing tables therein, thus no information about thepropagation path is kept. Instead, each node 100 is provided with arouting cache memory 104, the purpose of which is to keep certainentries that are used to identify packets that propagate there through.

The DD cache 403 is implemented as a routing cache in the TARP protocol.Storing of some entries within the DD cache 403 allows a node to deleteduplicate packets according to the Duplicate Discard process. Preferablythe DD cache 403 entry stores the ID of a packet and the time t, atwhich the stored ID of a packet is to be deleted.

Transmission Time Register.

A transmission time register 404 is used by a transmitter node tocalculate a transmission time Δt_(t) for the packet. The transmissiontime is calculated as a difference between a time at which the packet IDis provided to the Data Link Layer 204 and the time at which the DataLink Layer 204 returns a message that the packet is received by aneighboring node. The transmission time is further used to measure anaverage transmission time Δt_(avg), and calculate the time t_(r) atwhich DD cache 403 entries are to be deleted, where the DD processutilizes this transmission time.

Unlike the DD cache 403, the size of transmission time register 404 istypically sufficient to store an entry corresponding to only one packet.Specifically, the entry comprises the ID of a packet and time t_(b) atwhich this entry was stored into the transmission time register 404.

An entry from the transmission time register 404 is deleted when timeΔt_(b) expires, where this time ΔT_(b) is dependent upon the averagetransmission time Δt_(avg).

SPD Cache.

An SPD cache 401 is used by the Sub-optimal Path Discard (SPD), where anentry in this cache for use by an intermediate node K (FIG. 1) has thefollowing fields:

identification S of a node;

identification D of a node;

number of hops h_(dk) between D and the intermediate node K, where thisentry is a result of the most recent packet sent by D and addressed to Swhen it propagated through the intermediate node;

discard counter C_(sd) to be used by the process to control the flowfrom S to D;

number of hops h_(sk) between S and the intermediate node K, where thisentry is the result of the most recent packet sent by S and addressed toD when it propagated through the intermediate node;

discard counter C_(ds) to be used by the process to control the flowfrom D to S.

Every node stores a single entry [S, D, h_(sk), C_(ds), h_(dk), C_(ds)]that is used by two sessions between nodes: the one from S to D, and theone from D to S. Fields h_(dk) and C_(sd) are used by an S to Dcommunication session, while fields h_(sk) and C_(ds) are used by a D toS communication session. In this manner, only a single entry is storedfor packets propagating from S to D, and from D to S.

Every consecutive packet from S to D, or from D to S, alters thecontents of the SPD cache entry. Specifically, a packet sent by S to Dupdates fields h_(sk) and C_(ds), which are used by the SPD process tocontrol packet traffic flowing from D to S. Packets sent by D to Supdate fields h_(dk) and C_(sd), which are use to control packet trafficpropagating from S to D. Of course, the time at which a given entry inthe SPD cache 401 is deleted depends on the corresponding contents ofthe DD cache.

SPD Source Cache.

Similar to the SPD cache 401, an SPD source cache 402 is used by theSub-optimal Path Discard (SPD) process, where the SPD source cache 402stores an entry in its buffer in dependence upon each destination nodeto which a packet is transmitted. Thus, if source S transmits to threedifferent destination nodes, three different entries are stored in thebuffer.

The format of an entry stored in the buffer is as follows: ID of adestination node D, a number of hops h traveled by the latest packetfrom D to S, and mobility factor m of the packet for used by the SPDprocess for packet exchange from S to D. Similar to the SPD cache 401,the time at which a given entry is deleted from SPD source cache 402depends on the corresponding contents of a DD cache 403.

Node Processes.

Each node 100 executes independent processes, illustrated in FIG. 5,such as: a PacketTransmission process, PacketTransmissionResult process,PacketFwdRcv process, PacketFwdRcvResult process, and a CacheTimerprocess, described hereinbelow.

PacketTransmission.

This process transmits a new packet with entries └ID, r, h=0, h, m, m┘from a source node S. A packet being received from the Transport Layer202 triggers the PacketTransmission process. A flowchart of thePacketTransmission process is illustrated in FIG. 5A.

This process waits for a new packet from the Transport Layer 202. Assoon as this new packet arrives, the process checks if an entry in thetransmission time register 404 is empty. The Transmission time register404 stores at most one entry that comprises the ID of a packet and thetime at which that entry was made. The entry is made when the packetthat is distinguished by ID is provided to the Data Link Layer 204.

As mentioned before, the transmission time register 404 is used tomeasure a transmission time Δt_(t), which is the earliest time it takesthe Data Link Layer 204 to successfully transmit a packet to aneighboring node. Of course, since there is only space for only oneentry in this register 404, not every packet sent by a transmitting nodetakes part in these measurements.

If the transmission time register 404 is non-empty, it means that thePacketTransmission process has already provided a packet to the DataLink Layer 204, and the Data Link Layer 204 has not yet responded with amessage indicating whether the packet was received by a neighboring nodeor not. Thus, the Data Link Layer 204 is still busy transmitting aprevious packet. In such a case, the process fetches the time t_(b) fromthe transmission time register 404, and calculates the time that haselapsed since then. If this time is greater than the maximum time Δt_(b)for which the entry is to be stored in the register 404, a time forΔt_(b) has not been determined properly. Thus, Δt_(b) is doubled and thetransmission time register's 404 content is cleared.

If the transmission time register 404 is empty, the ID of a packet andthe current time are stored in the transmission time register 404, andthe values of h and m are then fetched from the SPD source cache 402.These values are the number of hops and a mobility factor, respectively,resulting from the last packet sent by destination node D and receivedby source node S. These two values correspond to a reverse communicationsession from nodes D to S and the SPD process uses these values.

The other two fields are number of hops h that a packet from nodes S toD has propagated, if the value for this field is 0, then the mobilityfactor m to be used by the SPD process is for a communication sessionfrom S to D. Optionally, mobility factor m is one of the TARP's modes ofoperation with a default value of 1.

Finally the process implements function dupDiscardAlg( ) that implementsthe DD process. The purpose of this function is to assure that if thepacket being transmitted returns to the source S, for example the packetis bounced back by the immediate neighbouring node, it is discarded as aduplicate. When function dupDiscardAlg( ) is called byPacketTransmission process, the function only inserts a packet to the DDcache 403. A call to dupDiscardAlg( ) made by process PacketFwdRcv, thatforwards and receives packets, is used to detect whether the receivedpacket is a duplicate.

The function uses the estimate of the average transmission timeΔt_(avg), stored by every node 100, and furthermore, at the end of thisprocess, the packet is provided to the Data Link Layer 204.

PacketTransmissionResult.

The PacketTransmissionResult process determines whether a neighbouringnode successfully receives a packet originated in the node and passed tothe Data Link Layer 204. The steps for this process are outlined in FIG.5B, where the result of this process is provided to the Transport Layer.This process is triggered by control message DLSuccTrans(ID) orDLFailTrans(ID) received from the Data Link Layer 204, and the ID of apacket comprises the identification of a node executing this process,where the node in execution of this process if the source of the packet.

This process waits for a control message from the Data Link Layer 204that concerns packet ID that had been passed there by the Network Layer203. It all happens at the source of packet ID.

First, the current estimate of the average transmission time is fetchedfrom the node's memory 104. Then, ID of a packet that the controlmessage concerns is compared with identification ID_(b) stored in thetransmission time register 404. If the entries match, the transmissionmoment of the ID packet is calculated by function getTransmissionTime( )and the contents of the register 404 is cleared since it is no longerneeded.

The purpose of this function is to calculate the time between the momentat which the packet identified by the ID is provided to the Data LinkLayer 204 and the moment at which the Network Layer 203 receivesDLSuccTrans(ID) from the Data Link Layer 204. This occurs if ID isstored in the register 404.

DLSuccTrans(ID) is the message that triggers this process, which meansthat the packet has been received by a neighbouring node. The processchecks the transmission time Δt_(t), if its value is positive, this isindicative that ID and ID_(b) match, and a new estimate of the averagetransmission time Δt_(avg) is calculated by a functionavgTransmissionTime( ). Regardless of the returned value, the processreturns NLSuccTrans(ID) message to the Transport Layer 202 notifying itthat the packet was successfully received by a neighbouring node. If theData Link Layer 204 is unable to send a packet to any neighbouring node,this layer provides message DLFailTrans(ID) to the Network Layer 203.Regardless of whether entries ID and ID_(b) match or not, which ischecked at the beginning of the process, the process returns theNLFailTrans(ID) message to the Transport Layer 202 notifying it that thepacket was not received by any neighbouring nodes.

If node K (FIG. 1) has n neighbouring nodes, then each of the nneighbouring nodes is capable of receiving messages transmitted by nodeK. Thus, the Data Link Layer 204 provides n DLSuccTrans messages to theNetwork Layer 203. Preferably, only the first DLSuccTrans messagetriggers Δt_(avg) calculation. The remaining messages are still providedto the Transport Layer 202, for which this information may be needed todetermine the number of neighbouring nodes. However, those messages nolonger trigger Δt_(avg) calculation because the transmission timeregister 404 is already cleared.

Preferably, control message DLFailTrans(ID) is not followed or precededby any DLSuccTrans(ID) messages. In other words, packet ID is eithersuccessfully sent, or no node confirms its reception. The latter case isequivalent to the situation in which the node effectively has noresponding neighbouring nodes.

Preferably successfully transmitted packets are used to measure theaverage transmission time Δt_(avg). Preferably thisPacketTransmissionResult process is triggered by the reception of DataLink Layer 204 messages, DLSuccTrans(ID) or DLFailTrans(ID), only at thesource of the packet they are related to, where corresponding processesat intermediate nodes are different.

PacketFwvdRcv.

The PacketFwvdRcv process is for processing data packet P with entries[ID, r, h] by a non-source node K, where this node K receives a datapacket from the Data Link Layer 204, which received the packet from aneighbouring node. The PacketFwvdRcv process is illustrated in FIG. 5C.

This process waits for a packet to be provided from the Data Link Layer204. A packet that propagates through an intermediate node K executesthis process. Node K obtains an estimate of the average transmissiontime from memory 104 and then calls function dupDiscardAlg( ) If theentry corresponding to the received packet already exists in the DDcache 403, then node K has already forwarded that packet to aneighbouring node, and the function returns ret_dupentry.

If the DD cache 403 does not have an entry corresponding to this packet,the function returns ret_newentry. In that case, node K checks the ID ofthe intended recipient of the packet. If node K is the only destinationnode of this packet, or one of many, since the packet is broadcast, thepacket's payload is provided to the Transport Layer 202. Thus, thepacket is received.

If node K is the only destination node of the packet, the processextracts a number of hops h that a packet has traveled and the mobilityfactor m used for communication session between nodes S and D. These twovalues, used by the SPD process are stored in the SPD source cache 402as h and m. These values are then provided back to source S in thetraffic from nodes D to S, assuming that node D transmits packets tonode S. Of course, this occurs if node K is the sole recipient of apacket. If a packet is broadcast, therefore the SPD source cache 402 isnot used because the address of the destination is D=0, and there is notraffic flowing in the reverse direction from other nodes to S, and ifnode K is the only destination node, the packet is removed from the AHN.

If node K is not an intended recipient of a packet, the processincrements the hop counter and checks if the packet had not circulatedin the AHN for too long. If the packet does circulate for too long, thenit is discarded.

Otherwise, the process calls function subPathDiscardAlg( ) where thisfunction implements the SPD process. The purpose of the SPD process isto further decrease the number of duplicate packets in the AHN.Depending on the outcome of this process, the packet is either discardedor further processed by node K. In the latter case, K relays the packetto its neighbouring nodes.

PacketFwdRcvResult.

The PacketFwdRcvResult process is used to determine whether a packetpropagating through the node executing this process has successfullybeen rebroadcast to a neighbouring node, as illustrated in FIG. 5D. Theinformation about the outcome of the transmission is used to calculatethe average transmission time. This process is triggered by controlmessages DLSuccTrans(ID) or DLFailTrans(ID) as received from the DataLink Layer 204. Furthermore, this process is triggered by the ID of thepacket not comprising the identification of a node executing thisprocess, which implies that the node executing this process is not thesource of the packet.

This process waits for a message from the Data Link Layer 204 directedto the packet ID.

The process is very similar to the process used in thePacketTransmissionResult process. The difference is thatPacketFwdRcvResult process does not return any messages to the TransportLayer 202. If the intermediate node cannot forward a packet to furthernodes because, for example all neighbouring nodes are gone or a packethas traveled too many hops, the Network Layer 203 does not respond. Aresponse is dependent upon the Transport Layer 202 for overseeing lostpackets. The fact that intermediate node K is unable to forward thepacket to another node does not imply that the packet will not reach itsdestination, other nodes may be able to forward the packet to adestination node.

CacheTimer.

The CacheTimer process, as illustrated in FIG. 5 e, controls entriesstored in the DD cache, SPD cache and SPD source cache, where thisprocess is triggered by a time-out of entry [ID, t_(r)] in the DD cachethat occurs when the current time is equal to t_(r). During the time ofΔT_(r), since the insertion or refresh of an entry distinguished by ID,no packet with that entry has propagated through the node in executionof this process.

This process executes asynchronously at every node, keeping track ofentries stored in the DD cache 403, SPD cache 401 and SPD source cache402. As soon as the time field in any DD cache 403 entry is equal to thecurrent time, which indicates that the particular entry has expired, theprocess removes the entry from the DD cache 403. If this is the lastentry concerning the communication session from nodes S to D, and fromnodes D to S, and the node executing the process is the source node S,the process removes the corresponding entry from the SPD source cache402. Preferably, source node does not store any information thatconcerns a communication session that most likely has already finished.

However, deleting an entry with identifications S and D from the SPDcache 401 requires that the DD cache 403 stores no entry with S and D,or D and S, as the identifications of source and destination nodes. Anentry in the SPD cache 401 stores information related to packetspropagating from nodes S to D and from nodes D to S. As long as at leastone entry for this pair of nodes is stored in the DD cache 403, whichindicates that a communication session between the two nodes is stillactive, the corresponding entry is preferably not deleted from the SPDcache 401, since this entry may be still useful for controlling packettraffic. In the above reasoning, it is assumed that expiry of entries inDD cache 403 means that the communication session is closed, howeverthis does not need to be the case.

If there is a temporary gap in a communication session between twonodes, then removing the entry from SPD cache 401 is premature. Theexpiry of entries in the DD cache 403 does not imply that thecommunication session is closed.

Preferably a separate timer is introduced for entries in SPD cache 401.This timer depends not only on the packet traffic in the AHN, but on themobility m of nodes as well. The disadvantage of this approach is thatit involves a higher complexity and thus larger memory requirements forthe SPD cache 401.

Initially, to simplify the implementation, preferably no timersassociated with the DD cache 403 are used to trigger discards from theSPD cache 401. In using this solution entries in the SPD cache 401 arestored as long as there is a memory space for them. A new entry forstorage into an already full SPD cache 401, preferably results in adiscard of the oldest entry from the cache 401.

Functions.

Processes described above invoke the following functions: dupDiscardAlg,getTransmissionTime, subPathDiscardAlg, deterministicDiscard,probabilisticDiscard, and avgTransmissionTime, as illustrated in FIG. 6.These functions implement processes that limit the number of duplicatepackets in the AHN, and perform other auxiliary operations.

dupDiscardAlg(ID, r, h, Δt_(avg))

The purpose of this function is to determine if the node that executesthis function has already received the packet with the given entry, asillustrated in FIG. 6A. If not, the given entry is inserted into the DDcache 403, otherwise the entry in the DD cache 403 is refreshed.Parameters that are provided to this function are the ID of a packet,maximum number of hops, current number of hops, and the averagetransmission time from this node. The function returns ret_dupentry, ifthe entry already exists, or ret_newentry if otherwise.

This function processes entries in the DD cache 403. First, itcalculates time Δt_(r) at which the entry determined from the givenpacket is to expire, where the packet's fields r, and h are used forthis purpose. The average transmission time Δt_(avg) is calculated inPacketFwdRcv or PacketTransmission Processes.

If the DD cache 403 already has stored therein the entry with ID, thismeans that the node executing this function has already processed thepacket. In that case, the entry in the DD cache 403 is refreshed. Inrefreshing this entry, the old time is updated with the new calculatedtime. This is likely to provide a more accurate estimate of the time forwhich the entry is stored in the cache 403. The function returnsret_dupentry, which informs the calling process that ID is a duplicate.

If the ID does not have a corresponding entry stored in the DD cache403, a new entry is created and stored in the cache 403. First, however,the function checks whether there is enough memory in the cache 403 forstoring of this new entry. If there is no space, the oldest entry thatcorresponds to the communication session belonging to ID is deleted. Inother words, the deleted entry is the one that describes a packet sentby nodes S to D, belonging to communication session s, such that thetimestamp t_(r) is minimum.

If ID is the first packet belonging to its communication session, thenthe globally oldest entry is deleted.

Finally, the function returns ret_newentr, which informs the callingprocess that ID is a new packet.

getTransmissionTime(ID, Δt_(avg)).

This function calculates the time between the moment at which a packetID is stored in the transmission time register and the current time, asillustrated in FIG. 6B. Parameters that are provided to this functionare the ID of a packet and the current estimate of the averagetransmission time Δt_(avg), where this function returns calculated time,or 0, if there is no entry corresponding to the ID in the transmissiontime register.

This function first checks if the ID passed as an argument matches theidentification stored in the transmission time register 404. If it doesnot, calculation of the transmission time Δt_(t) taken for the Data LinkLayer 204 to send that packet is not possible, thus the function returnsa 0.

If the identification stored in the transmission time register 404matches that of the packet, then the transmission time Δt_(t) iscalculated. This time is calculated as the time that has elapsed sincethe storing of ID in the transmission time register 404. This isfollowed by the calculation of a new estimate of Δt_(b), which is themaximum time for which the entry is stored in the register. This entryis then set to twice that of Δt_(avg), and the value is updated byfunction avgTransmissionTime( ). This preferably assures that thetransmission time register 404 entry is not deleted too early. Finally,the transmission time is returned.

subPathDiscardAlg(S, D, h, h, m).

The purpose of this function is to use the SPD process to limit thenumber of duplicate packets flowing from source node S to destinationnode D, as illustrated in FIG. 6 c. Parameters that are provided to thisfunction are the source node S of a packet, its destination node D,number of hops h it has traveled so far (i.e. h_(sk)), number of hops hthat the last packet from nodes D to S has traveled, and mobility factorm, to be used by the SPD process for a communication session from nodesD to S. The function returns ret_discard if the packet for which thisfunction was called is to be discarded, or ret_keep, if the packet is tobe kept.

This function implements Sub-optimal Path Discard (SPD) process whosepurpose is to limit the number of packets in the AHN that propagatealong sub-optimal paths. Every node has stored therein a SPD cache 401,the entries of which store the following fields: [S, D, h_(sk), C_(ds),h_(dk), C_(sd)]. A single entry will be used by two sessions: the onefrom S to D, and the one from D to S. Fields h_(sk) and C_(ds) are usedby a S->D communication session, while fields h_(dk) and C_(sd) are usedby a D-S communication session.

FIG. 7 illustrates three nodes, S, D, and K. Node K is disposed betweennodes S and D. The intermediate node K receives a packet sent by sourcenode S and is addressed to node D, node K checks whether the SPD cache401 has stored therein an entry corresponding to a communicationsession, in either direction, between nodes S and D. If the entryexists, the number of hops h_(sk) that the packet has made so far isstored in that entry, thus overwriting the old value. If the entry doesnot exist, which means that is the first packet belonging to an S-Dcommunication session, the process creates a new entry with S, D, andh_(sk) set to h, which is the number of hops that a packet has made sofar. Remaining fields that are other than S and D, are set to zero.

The process extracts h_(dk) from the SPD cache 401. The positive valueof h_(dk) keeps the number of hops between D and K made by a packetpropagating from D to S. This entry was previously created in the SPDcache 401 when a packet from D to S propagated through node K at a priortime. If h_(dk)=0, then this entry has just created in the SPD cache401.

If h_(dk) is positive, the process calculates the new value for thiscounter. This calculation starts with an evaluation of two inequalities.In the first, it just checks the value of h, which is the number of hopstaken for the last packet to propagate from D to get to S. This value isinserted into the packet by process PacketFwdRcv and is propagated inthe packet sent by nodes S to D.

Furthermore, if this value is positive, the process evaluates anotherinequality:h <(h _(sk) +h _(dk))

where this inequality checks whether the path h of the last packet fromD to S, received by S, is shorter than the sum of two paths. These pathsare: the current path from nodes S to K made by the packet that iscurrently being sent, and the old path from D to K made by the lastpacket sent from nodes D to S, as illustrated in FIG. 7.

A source of a packet is not always aware of a value for h, that is, thelength of the path made by the last packet received from thedestination. This occurs, for example, when a source node sends a veryfirst packet in a communication session. In such a case, the source setsset h to 0. An intermediate node calculating a discard counter detectsthis value for h, and also set it also to 0. This will effectivelydisable an SPD process, where the SPD process activates as soon as thesource receives the first reply from a destination.

FIG. 8 illustrates nodes S and D, having a first path that involvespropagation intermediate nodes K, L and M, and a second path thatinvolves propagation through a single intermediated node Z.

If this aforementioned inequality is met, then it typically implies thatpackets from node D are reacheable by node S via path shorter than theone propagating through node K. A packet from S to D preferably triggersthe above calculation that is further utilized by packet trafficpropagating in the opposite direction from nodes D to S.

If the inequality holds the topology of the AHN preferably remains suchthat node K is not on the shortest path from D to S. This means thatnode K preferably discards packets sent by D to S, since other nodeslocated on the shortest path—second path—from D to S relay those packetsfaster.

An amount of packets for propagating between nodes D and S that are tobe discarded depends on the value of discard counter C_(ds). The counteris set to the new value if the above condition holds, where this valueis calculated after h_(sk) is updated from the packet header by thefollowing:C _(ds) = m *└(h _(sk) +h _(dk))− h _(—)

where m≧0 is a mobility factor carried by the packet.

Note that according to the process C_(ds) is set to zero if h=0.Assuming that h is positive and m=1, C_(ds) represents a difference inhops between an estimated length of a path that a packet travels betweennodes S and D, and the length of the path traveled by the last packetfrom D to S, which was at the time the shortest path between D to S.

Node K starts discarding packets sent by D to S while at the same timedecrementing C_(ds). As soon as C_(ds) becomes 0, node D resumesforwarding of packets that are addressed to node S. Details of thisprocess are implemented in functions deterministicDiscard( ) andprobabilisticDiscard( ).

If a packet from node S to D triggers a call to functionsubPathDiscardAlg( ) like in the case discussed in this section, discardcounter C_(sd) is provided to the discard functions. In this case h_(dk)is updated from the packet header by the following:C _(ds) =m*└(h _(sk) +h _(dk))− h _(—)

where m≧0 is a mobility factor carried by the packet. The discardfunctions decide whether the packet from S to D, for which this functionis called, is to be discarded or forwarded.

Note that if subPathDiscardAlg( ) is called with D and S as itsarguments, triggered by a packet traveling in the opposite directionfrom D to S, C_(ds) is provided to these functions, not C_(sd). In sucha case, the SPD process calculates a new value of C_(sd) used by acommunication session from S to D and then determines whether the packetfrom D to S should be discarded.

In the meantime, another packet sent by S to D is optionally received byK, and yields C_(ds)>0. This will mean that packets sent from nodes S toD are still following paths shorter than the one via node K. In such acase, according to the process, the old value of C_(sd) is overwrittenby the new value.

The discard functions for a packet traffic flowing from S to D arecalled if the relevant discount counter C_(sd)>0, and the discountcounter C_(ds), before the process calculates its new value, ispositive.

At some point the value of a discount counter may drop to 0. When thatoccurs, node K is not only used to relay the packet, but also change theestimate of the shortest path h to the length of the path from nodes Sto D via node K. This is very important in handling a situation in whichthe AHN topology change to a deletion of the shortest path. If h is notaltered, nodes downstream are not be aware of the topology change andkeep deleting the packets.

A packet traveling from nodes S to D triggers a calculation of a discardcounter later used by the process to determine the fate of a packettraveling from D to S. In other words, traffic from S to D determinesthe behavior of the SPD process for packets flowing in the oppositedirection, from D to S.

A period for which a node discards packets depends on the estimateddifference between another path and the shortest path. At any time,topology of the AHN changes and the shortest path is no longer there. Ifthe path difference is large, there is a good chance that other nodes“closer” to the shortest path will pick up the transmission. Thispotentially results in node K no longer forwarding packets from nodes Dto S for a relatively long time.

If this difference is small, node K has less latitude, since any changeof topology may place K on the shortest path between S and D. The SPDprocess preferably functions in the bi-directional packet trafficscenarios. If all the source node does is broadcasts packets, withdestination nodes that are acting as passive receivers, this processpreferably remains inactive. For example, when node S transmits packetsto D and there is no traffic flowing in the opposite direction from D toS, preferably C_(sd), as well as C_(ds), remain with zero values and theprocess relays all packets from S to D.

If C_(sd) and C_(ds) are both positive then it means that most likelythe path through node K is not the shortest between nodes S and D andthe packet is discarded either deterministically usingdeterministicDiscard( ) or probabilistically using proabilisticDiscard(). Considering only use of the deterministicDiscard( ) process for now apacket travelling from S to D is discarded, counter C_(sd) isdecremented. If a packet travelling from D to S is discarded, C_(ds) isdecremented. If either of the counters are zero then the packet isforwarded.

Accordingly the impact of the mobility factor m, discussed below,becomes apparent. If m=0 then the SPD process is disabled. With mincreasing each of the C_(sd) and C_(ds) counters increase and morepackets are discarded. In other words, SPD avoids suboptimal paths moreaggressively. Conversely, if m is small, the counters C_(sd) and C_(ds)decrease to zero faster, thereby allowing packets to utilize suboptimalpaths. This for example being beneficial for example where the physicalmobility of the nodes within the AHN is higher.

Mobility Factors m and m

The mobility factors m and m are used in the aforementioned formulassince they have a relation to the mobility of packets in the directionsfrom S to D and D to S respectively. In cases of high packet mobility, mand m are preferably set to 0, thus effectively turning off SPD process.In the case when this process is disabled, TARP relies on a simpleDuplicate Discard process implemented in function dupDiscardAlg( ).

Mobility factors m and m are used to determine how many duplicatepackets a node is to discard. With increasing m and m, the number ofpackets also increases, making the protocol less reactive to AHNtopology changes. This suggests that when the AHN is very mobile, orwhen a successful packet delivery between a source node and adestination node is preferable, then m and m should be set to smallvalues, with the minimum of 0.

The mobility factor is set dynamically by the TARP, where its value isdependent upon a packet loss as perceived by the application 201. If thepacket loss becomes high at any time, the application 201 dynamicallysets m, and thereby m, to 0, thus forcing the protocol to forward morepackets.

The mobility factor is set by node S, and propagated as m in the packetfrom S to D, and is later returned, as m, and propagated in the packetfrom D to S. Traffic from S to D determines behaviours of a process forpackets traveling from D to S. If node S is to affect the process, itsvalue is preferably propagated in the packet in the reverse traffic tonode S.

In this manner, source S is able to control the operation of the SPDprocess that limits the number of packets that are on the sub-optimalpath. If the process is aware that the mobility of the AHN is low, theprocess optionally sets m to a higher value, for example that of 2 or 4.If, on the other hand, the source node detects a large number of droppedpackets in the AHN, or it is aware that the AHN topology changes arelikely to be frequent, m is preferably set to 0, effectively disablingthe SPD process, and forcing the intermediate nodes to pass all packetsfrom S to D. This is of course subject to constraints implemented by theDD process described hereinbelow.

As aforementioned, FIG. 8 illustrates a simple AHN topology for thefollowing example. There are two paths between S and D: the shortest2-hop path occurs via node Z and a longer 4-hop path occurs via nodes K,L, and M. Assuming the mobility factor m=1 and that both S and Dtransmit packets to each other.

Inspecting the contents of SPD cache 401 entries at nodes K, L, and M,and SPD source cache 402 entries at nodes S and D, as well as relevantpacket fields h and m at several stages of the communication, thefollowing result:

SPD source cache 402 at a source node of the packet are set by processPacketTransmission

SPD source cache 402 at a destination node of the packet are set byprocess PacketFwdRcv

SPD cache 401 at an intermediate—transit—node of the packet are set byfunction subPathDiscardAlg and called by process PacketFwdRcv.

FIG. 9A illustrates a table showing SPD source cache 402 entries fornodes D and S for a packet p1 sent by D to S and arriving at node S. SPDsource cache 402 at node D has not yet received any packet from S, soinitially the path h from D to S and the mobility factor m are set to 0.The SPD source cache 402 at node S has received the packet from D.Assuming that the packet traveling the shortest path via Z arrived andfirst, the length of the path is 2, since S has learned the mobilityfactor in node D's application is 1.

FIG. 9B illustrates the SPD cache 401 entries at nodes K, L, and M. Thepacket traveling from D to S carries values of path and mobility factorh= m=0. The packet has made 1 hop to M (h_(dm)=1), 2 hops to L(h_(dl)=1), 3 hops to K (h_(dk)=3). Since no packet from S to D has beensent yet, the remaining fields of the new entries in the SPD cache 401entries at three nodes are set to 0. The packet is not dropped becauseC_(ds) is 0.

FIG. 9C illustrates a reverse of that shown in FIG. 9A, where a packetp2 of a reverse communication session from S to D arrives at node D,where this operation is potentially node S′ reply to the receipt ofpacket p1. Thus, the SPD source cache 402 at node D has received thepacket from S. Assuming that the packet traveling the shortest path viaZ arrived first, the length of the path is 2. D has learned that themobility factor in the node S′ application is 1. The SPD source cache402 at node S has the value for the mobility factor and the length ofthe shortest path h from D to S set upon reception of packet p1.

FIG. 9D illustrates the SPD cache 401 entries at nodes K, L, and M,where the packet traveling from nodes S to D carries values of path h=2and mobility factor m=1. The packet has made 1 hop to K (h_(sk)=1), 2hops to L (h_(sl)=2), and 3 hops to M (h_(sm)=3). The packet carriespositive values of h and m, and both conditions, as required by the SPDprocess for a calculation of the discard counter C_(ds), are fulfilled.This calculation sets C_(dk) to 2 at all intermediate nodes. This valuecorresponds to the difference—in hops—between the length of the S to Dpath via nodes K, L, and M, and the shortest path via node Z. SinceC_(sd) is still 0, packet p2 traveling from S to D via node K is notdropped until it gets to node D. The Duplicate Discard (DD) processpreferably drops packet p2 at node D.

FIG. 9E illustrates SPD cache 401 entries at nodes K, L, and M, where apacket p3 is sent by nodes D to S for arrival at node S, which in turnis potentially seen as D's reply to p2. The entries at SPD source cache402 at nodes S and D remain unchanged. The packet traveling from D to Scarries values of path h=2 and mobility factor m=1. The packet has made1 hop to M (h_(dm)=1), 2 hops to L (h_(dl)=2), 3 hops to K (h_(dk)=3).Packet p3 carries positive values of h and m, and both conditions,according to the SPD process required for a calculation of the discardcounter C_(sd), are fulfilled. This calculation sets C_(sd) to 2 at allintermediate nodes.

According to the SPD process, the value of C_(sd) upon arrival of thepacket and value C_(ds) are preferably positive in order for a node tocall a discard function to discard a packet traveling from D to S.Although C_(ds) is positive, the value of C_(sd) upon the arrival ofpacket p3 at intermediate node is 0. That is why the packet ispreferably not discarded but relayed further.

Assume that C_(sd)>0 is sufficient for a node to call a discard functionand to possibly drop a packet traveling from D to S. This packet ispreferably not dropped immediately by the first neighbouring node ofnode D, that is, node M, and remaining intermediate nodes K, and L donot see that packet. Thus, preferably node M sets C_(sd) to a positivevalue, and the other two nodes, unaware of the traffic from D to S, keepC_(sd) set to 0. Recall that C_(sd) is used to discard duplicate packetsflowing from S to D. If now node S sends a packet to D, nodes K and Lrelay that packet because their C_(sd) values are 0. The duplicatepacket is thus discarded by node M, that is, the neighbouring node ofthe packet's destination.

Of course, this approach would waste AHN resources. A packet would berelayed unnecessarily through the AHN, along almost an entire path, onlyto be dropped by the destination's neighbouring node.

If the SPD process requires both values of discard counters to bepositive, all intermediate nodes relay packet p3 from D to S, thussetting a value of the discard counter for the traffic flowing from S toD. Now, duplicate packets sent by S are discarded by node K, which isnode S′ neighbouring node, rather than node M.

FIG. 9F illustrates the SPD cache 401 at nodes K, L, and M, where apacket p4 of a reverse communication session from nods S to D arrives tonode D, where this is potentially node S′ reply to packet p3. The SPDsource cache entries at nodes S and D, remain unchanged. The packettraveling from S to D carries values of path h=2 and mobility factorm=1, therein. It has made 1 hop to K (h_(sk)=1). This time, Cs_(d) iscalculated when packet p3 passes through K from D to S, and is positive.Depending on the discard process used, packet p4 is discarded as aduplicate either with probability 1, if function deterministicDiscard( )is used, or a positive probability less than 1, when functionprobabilisticDiscard( ) is used. In any case, C_(sd) is decremented to1.

FIG. 9G illustrates the SPD cache 401 at nodes K, L, and M, where apacket p5 sent by node D to node S arrives at S, where this ispotentially node S′ reply to packet p4. The entries in the SPD sourcecache at nodes S and D remain unchanged. If packet p4 sent from S to Dis discarded at K, a copy thereof arrived at node D following theshortest path via node Z. Thereafter, node D replies with packet p5, andthis packet finds a positive value of a discount counter C_(dk). Adiscard function is called and potentially packet p5 is discarded andC_(ds) is decremented. As before, the packet carries values for path h=2and mobility factor m=1.

FIG. 9H illustrates the SPD cache 401 at nodes K, L, and M, where aftertransmission of packet p6 from S to D, packet p7 from D to S, and packetp8 of a reverse communication session from S to D. The SPD source cache402 entries at nodes S and D remain unchanged. Packets p6 and p7 havetheir discard counters both set to 0, which means that packet p8 findsC_(sd)=0 at node K. According to the SPD process, a value of h in thepacket is set to 4, that is, the length of the path between S and D vianode K with mobility factor m still being 1. The packet is relayed andthe value of h propagates to nodes L and M. Each of these nodes relayspacket p8 because the new, high value of h is such that the inequalitydeciding whether the packet should be discarded or not does not hold.

Packet p8 is discarded by the destination D. It is discarded because itscopy has arrived first following the shortest path via Z. A couple ofpacket exchanges between D and S reset the discard counters back topositive values because the values of h, stored by S and D, stillcorrespond to the length of the shortest path, which is 2.

This mechanism, in some sense, reinitiates the SPD process after thediscard counters drop to 0. This is preferable for the AHN to detect anew shortest path. After h in the SPD source caches 402 at nodes S and Dis set to 2, node Z turns off. Thus, the shortest path via node Z isgone. Nodes K, L, and M on the other path will not detect this removalof node Z immediately. Thus, nodes K and M discard packets flowing fromS to D, and from D to S, respectively, until the discard counters dropto 0. This allows the packets to be relayed over that path and updatesthe value of h from 2 to 4 at both nodes S and D. This value, carriedlater in subsequent packets, allows the SPD process to detect the newshortest path—the one that leads through nodes K, L, and M. Without thismechanism, the SPD process potentially consumes more time in order tolearn about the AHN topology change and about a new shortest path. Aftersome time, packets are relayed by M and K only to be dropped by node L.Packets finally reach their destinations after the discard counter atnode L has dropped to 0.

deterministicDiscard(C_(sd)).

The purpose of this function is, on the basis of the discard counterstored in the SPD cache, to decide deterministically whether a packet isto be discarded, as shown in FIG. 6D. The discard counter C_(sd) isprovided to the function and the function returns ret_discard if thepacket for which this function was called is to be discarded, or thefunction returns ret_keep, otherwise.

The mobility of nodes in the AHN, and the fact that any node can beturned-off at any time, means that at some point, node K resumesrelaying packets from S to D. Otherwise, if the shortest path is gone,node D stops receiving any packets from S. Thus, function implements adeterministic approach to this problem.

If discard counter C_(sd) is positive, it is decremented and the packetis discarded. Otherwise, if C_(sd) is zero, the packet is forwarded.Unless a new packet from D to S changes the value of C_(sd), the nodeexecuting this process drops C_(sd) packets. Then, it resumes theirforwarding.

probabilisticDiscard(C_(sd), C_(sd) ^(init))

The purpose of this function, on the basis of the discard counter storedin the SPD cache, is to decide probabilistically whether a packet is tobe discarded or not as illustrated in FIG. 6E. Two arguments areprovided to the function, namely discard counters C_(sd) and C_(sd)^(init). The function returns ret_discard if the packet for which thisfunction was called is to be discarded, or ret_keep, otherwise.

This function is used for controlling the time for which a node is toinitiate a discarding of packets. C_(sd) ^(init) is used to store aninitial value of C_(sd) calculated by the node for a communicationsession from S to D, and C_(sd) ^(init) for communication session in theopposite direction. Thus, when node K creates a new entry for source Sand destination D, or updates an old entry with the h informationextracted from the packet traveling from D to S, both C_(sd) and C_(sd)^(init) are set to the same value.

The probabilistic method checks if the discard counter C_(sd) at node Kis snit positive. If the counter is positive, the method decrements it,leaving C_(sd) intact. However, a decision as to whether that packet isto be relayed or dropped is now based on a random decision. Moreprecisely, the packet is relayed to another node with the followingprobability:P _(disc) =C _(sd) /C _(sd) ^(init)

According to this formula, every consecutive packet sent by S to D has agreater probability of being dropped than its predecessor. This meansthat as time goes by, and no packet from D to S has been observed forresetting the values of C_(sd) and C_(sd) ^(init), it is more likelythat the AHN topology has changed, thus placing node K on the shortestpath from S to D. In such a case, it is potentially preferably toforward the packet with some probability.

avgTransmissionTime(Δt_(t)).

The purpose of this function is to calculate the average transmissiontime at the node that calls this function for execution. The functionsteps are illustrated in FIG. 6F. Arguments that are provided to thefunction are the last recorded transmission time, where the functionreturns the new estimate of average transmission time Δt_(avg).

The formula used for the calculation gradually decreases the importanceof past samples and increases the importance of the recent ones. Abigger C_(avg) puts more emphasis on the history, while a smallerC_(avg) favors recent measurements. Typical acceptable values arebetween 0.5 and 0.8. The value of C_(avg) is one of the protocol'sparameters that is controlled by the application 201 through a mode ofoperation.

Timeout of DD Cache Entries.

This method is implemented in order to calculate a time ΔT_(r) afterwhich the DD cache 403 timer for a given entry in the cache is toexpire. The following parameters are used within this method, where r isthe maximum range of a packet expressed in hops. A packet is removedfrom the AHN when it makes r hops and does not reach the destination.Another parameter h is the number of hops a packet has traveled so far,and ΔT_(avg) is the average time for a node to successfully transmit apacket to an existing neighbouring node avgTransmissionTime( ) wherethis includes the time for possible retransmissions on lower NetworkLayers 203.

Every time a packet arrives to node K, that node checks whether theentry corresponding to this packet exists in the DD cache 403 using thedupDiscardAlg( ) process. If the entry does not exist, the new entrycorresponding to this packet is created and stored in the cache. Thetime ΔT_(r) after which that entry is discarded is approximated by thefollowing formula:T _(r) =F(p)*Δt _(avg)wherep=r−h,

is the number of hops that a packet travels before it arrives to thedestination, or if the destination cannot be found, before it isdiscarded. A function F is defined in such a way that:F(p)ε[0, p−1]

Function F assumes that a maximum value of p−1 is the maximum allowednumber of hops that a packet is left with and is decreased by 1. If p−1is multiplied by ΔT_(avg), it provides a latest time at which the packetreturns to the node, assuming that every node has a similar transmissiontime. Such a returned packet is discarded as a duplicate packet.

Assuming that F[p]=0, the minimum value, the entry corresponding to thepassing packet is not stored in the DD cache 403. Such a protocol infact corresponds to a simple flooding controlled only by the time tolive field r for the packet.

FIG. 10 illustrates an example where setting F(p) to its maximum valueof p−1 is potentially beneficial, as outlined hereinbelow. As is shownin FIG. 10, all by p−1 nodes form a loop. Node K forwards the packetthat has p=5 hops to live. From this figure it is evident that if node Kuses F(p)<(p−1)Δt_(r), the relevant entry is discarded too early. Inthat case, when the packet gets to node K, after making a full loop, itis forwarded further, which unfortunately wastes AHN bandwidth. In thisexample it is assumed that node C cannot receive the transmission from Kbecause when that transmission was taking place, node C was too far fromnode K. On the other hand, if K uses F(p)=p−1, it never forwards aduplicate but instead will reserve more memory for the DD cache 403.

If B or C are in reception range for receiving the transmission from K,then using F(p)<(p−1) potentially leads to premature deleting of therelevant entry from the DD cache. Thus, function F potentially dependson its argument p in yet another way. With a large p, the chance thatall p nodes form a loop, thus making it more likely for a node to see apacket's duplicate, becomes less probable. On the other hand, if thereare just a few nodes, hence a small p, the chance that these nodes forma loop becomes higher. This suggests that when p is small, F(p) shouldbe closer to p−1, than when p is large.

Taking this into consideration, on the average, approximating F(p) by0.75*(p−1) provides the right compromise between the bandwidth andmemory usage. Simulations of some typical scenarios likely show whatvalue of F(F(p)) gives the best results, and how the number of hops thata packet is left with affects the optimal value of F(p). Δt_(avg) ismeasured, stored and updated by every node. In this manner, every nodeuses its own estimate of Δt_(x.)

Of course, it is not necessarily true that every node has the sametransmission time, and that is why Δt_(x) is only a rough estimate.Preferably, the entries in the DD cache at the source of a packet arelikely kept longest. This occurs because at the source, h=0, and Δt_(x)assumes the maximum value.

TARP Parameters and their Initial Values.

TARP has only five parameters, whose initial values are initially set,where the first two are later maintained by the protocol itself in orderto keep their values optimal. The last three are included in protocolmodes of operation and are controlled by the application 201 designeror, dynamically, by the application 201 itself.

The first value is the average time Δt_(avg) between the moment a packetis passed to the Data Link Layer 204 and the moment at which Data LinkLayer 204 notifies the Network Layer 203 if the packet is successfullyreceived by a first neighbouring node. This time is used in calculationof time ΔT_(r) for which an entry is stored in the DD cache 403.Assuming knowledge of the maximum packet length L and AHN's capacity C,Δt_(avg) is initially approximated by c*(L/C), where c>1. The protocoladjusts Δt_(avg) to the value closer to the actual average timeΔt_(avg), using the PacketTransmission process and avgTransmissionTime() function. Having Δt_(avg)=0, will not cause a failure of the TARP.

However, setting Δt_(avg)=0, results in a premature expiry of the firstfew entries in the DD cache that leads to more copies of the packetsthey correspond to circulating in the AHN. Advantageously, the TARPconverge to a correct value of Δt_(avg).

The second value is the maximum time Δt_(b) for which an entry is to bestored in the transmission time register. It is assumed that the initialvalue of Δt_(avg) is positive, Δt_(b)=c*Δt_(avg), where c>1 andΔt_(b>>)0, otherwise calculating of a good estimate for Δt_(avg) is moredifficult. This operation is performed using the PacketTransmissionprocess.

The third parameter C_(avg) is used in calculation of the averagetransmission time Δt_(avg).

The value of C_(avg) emphasizes either the past or recent measurementsof Δt_(avg). According to the formula used to calculate Δt_(avg), a nodewill react slower to changes of the actual transmission time if C_(avg)is too large. Depending upon the environment in which the TARP operates,different values of C_(avg) are potentially optimal. This parameter ispotentially controlled by the application through some mode ofoperation. Preferable values for C_(avg) range between 0.5 and 0.8, thusfor example C_(avg) is initially set to 0.65.

The fourth parameter is ΔT_(r), where the function F used to determinedan approximate timeout ΔT_(r) for use in determining when an entry is tobe removed from the DD cache 403. Using an aforementioned equation:F(p)=0.75*(p−1) seems to be a right approximation if the amount ofmemory used within each of the nodes is limited. Otherwise, F(p)=p−1 issafest measure as it assures that minimal bandwidth will be wasted inthe AHN. Optionally, this parameter is controlled by the application 201through a mode of operation.

A fifth parameter is the mobility factor m, where the mobility factor isused to calculate the value of discount counter used by the SPD processthat is further used in function subPathDiscardAlg( ). The default valueof m=1 seems to be a safest discount value with this value closelyapproximating a difference—in hops—between the current path for packetpropagation and the shortest path for packet propagation. Optionally,similar to parameter C_(avg) and function F, the mobility factor iscontrolled by application 201 through a mode of operation.

TARP Properties.

The TARP advantageously allows for further simplification for AHNapplications that are used in an undemanding environment. For example,such an environment is a small collection of nodes that are involved ina low-bandwidth communication.

An argument provided to the TARP is used to determine the level of thecomplexity desired by the application 201. In the simplest case, theflooding on which the TARP is based is controlled only by time to live rfor a packet. Thus, there is little need for a DD cache 403 ortransmission time register 404. Every node forwards packets addressed toother nodes and receives and removes from the AHN packets addressed toit. Furthermore, packets that circulate in the AHN too long, based on rand h, are also removed. Achieving of simple flooding is accomplished bysetting function F (p)=0 and m=0.

If a simple method of flood control is needed, then F(p)>0 and m=0 isutilized. This activates the first method that controls the number ofpacket duplicates traveling in the AHN, but disables the second methodthat limits the number of packets on sub-optimal paths.

If the bandwidth of the AHN is very scarce, both the DD process and theSPD process are used by setting F(p)>0 and m>0. In addition to theseparameters, a value of parameter C_(avg) used in calculation of theaverage transmission time Δt_(avg), where Δt_(avg) is optionally varieddepending on the predicted or perceived mobility of the AHN.

Environment of an ad-hoc application, and resulting requirements imposedon the TARP, might be represented as a single “complexity level”parameter. This parameter optionally assumes different values fordifferent combinations of the above three modes of operations. This way,a designer of an ad-hoc application 201 tailors TARP to the needs of theapplication and its environment.

Advantageously, the TARP is simple over those protocols envisaged in theprior art. The advantages are realized because no routing tables areutilized, no sophisticated methods are employed for maintaining of aroute within the AHN once the route is established, and flexibility inreacting to AHN topology changes. Furthermore, control messagesexchanged between nodes are very limited, and there are five protocolparameters used for controlling of the AHN.

Replication of a packet at many nodes assures that the packet will getthrough to a destination node, assuming of course that destination nodeis not in a disjoint part of the AHN. Advantageously, by discardingduplicate packets through the implementation of the DD process,uncontrolled replication of packets that would quickly occupy most ofthe AHN's bandwidth, is advantageously reduced. A number of duplicatepackets is further limited by the SPD process, which discards packetstraveling on sub-optimal paths.

Since the TARP uses controlled flooding, broadcasting is facilitated.Furthermore, duplicate packets do not occupy as large portion of theAHNs bandwidth as do control messages, used in more complex protocols,which are used to assure that packets follow optimal paths. Thesecontrol messages not only increase the complexity but also involve asignificant overhead in terms of wasted bandwidth.

Furthermore, the TARP complexity is further reduced, and its performanceimproved as a result, because at the Network Layer 203 there are noacknowledgement messages, or any other communication between thedestination and the source. The TARP advantageously forwards packets todestinations.

If an application needs a reliable transfer of data, higher levels ofthe TARP are optionally responsible for handling acknowledgements andretransmissions. This way, if an application does not need a reliabletransfer of data, thus for example a packet is broadcast to make anothernode aware of its existence, the TARP does not waste any bandwidth onacknowledgements.

Finally, the TARP modes of operation provide an easy method of adjustingto different requirements imposed on the AHN.

Numerous other embodiments may be envisaged without departing from thespirit or scope of the invention.

1. A method of providing a reactive ad-hoc network comprising the stepsof: (a) providing at least a source node, a first node, a second othernode, and a destination node of a plurality of nodes, each nodecomprising at least a processor, a memory, and a transceiver incommunication with the processor for receiving data and transmittingdata via a wireless communication medium; (b) providing a packet of datacomprising message data and header data to the processor of the firstnode for transmission therefrom, the header data comprising datarelating to the source node and the destination node for the packet ofdata, data relating to a number of hops already completed for the packetof data, data relating to mobility of packets of data within thereactive ad-hoc network transmitted from the source node to thedestination node and the destination node to the source node, datarelating to a number of hops between the source node and the destinationnode for a previous packet of data, and a unique identifier for thepacket of data; (c) transmitting the data from the transceiver of thefirst node in a broadcast fashion; (d) receiving the data at thetransceiver of the second other node; (e) calculating at the secondother node a discard counter, the discard counter determined independence upon at least the direction of the packet relative to thesource node and destination node, a packet mobility factor in thedirection of the packet, the number of hops from the source node to thesecond other node, the number of hops from the destination node to thesecond other node and the number of hops between the source node anddestination node for a previous packet of data; (f) determining whetherto discard the packet in dependence upon at least the discard counter;and (g) discarding the packet and decrementing the discard counter wherethe determination is made to discard.
 2. A method according to claim 1further comprising: repeating steps (f) and (g) for subsequent packetsbetween the source node and destination node in the direction of thepacket until either a subsequent packet is received in the reversedirection to the packet and the discard counter is recalculated or thediscard counter reduces to zero.
 3. A method according to claim 2further comprising: (h) re-starting to forward packets from the secondother node when the discard counter becomes zero.
 4. A method accordingto claim 1 wherein the data relating to mobility of packets of datawithin the reactive ad-hoc network is determined by an application inexecution upon the source node.
 5. A method according to claim 4 whereinthe application establishes the data relating to mobility of packets ofdata in dependence upon at least one of a measure of physical nodemobility, a measure of topology change, and a measure of packets losswithin the reactive ad-hoc network.
 6. A method of providing a reactivead-hoc network comprising the steps of: (a) providing at least a firstnode, a second other node, a source node and a destination node of aplurality of nodes, each node comprising at least a processor, a memory,and a transceiver in communication with the processor for receiving dataand transmitting data via a wireless communication medium; (b) providingpacket of data comprising message data and header data to the processorof the first node for transmission therefrom, the header data comprisingdata relating to the source node and the destination node for the packetof data, data relating to a number of hops already completed for thepacket of data, data relating to mobility of packets of data within thereactive ad-hoc network transmitted from the source node to thedestination node and the destination node to the source node, datarelating to a number of hops between the source node and the destinationnode for a previous packet of data, and a unique identifier for thepacket of data; (c) transmitting the data from the transceiver of thefirst node to the transceiver of the destination node withoutmodification via the second other node other than the first node or thedestination node absent a known available route; and (d) calculating atthe second other node a discard counter, the discard counter determinedin dependence upon at least the direction of the packet relative to thesource node and destination node, a packet mobility factor in thedirection of the packet, the number of hops from the source node to thesecond other node, the number of hops from the destination node to thesecond other node and the number of hops between the source node anddestination node for a previous packet of data; (f) determining whetherto discard the packet in dependence upon at least the discard counter;and (g) discarding the packet and decrementing the discard counter wherethe determination is made to discard.
 7. A method according to claim 6further comprising: repeating steps (f) and (g) for subsequent packetsbetween the source node and destination node in the direction of thepacket until either a subsequent packet is received in the reversedirection to the packet and the discard counter is recalculated or thediscard counter reduces to zero.
 8. A method according to claim 7further comprising: (h) re-starting to forward packets from the secondother node when the discard counter becomes zero.
 9. A method accordingto claim 6 wherein the data relating to mobility of packets of datawithin the reactive ad-hoc network is determined by an application inexecution upon the source node.
 10. A method according to claim 9wherein the application establishes the data relating to mobility ofpackets of data in dependence upon at least one of a measure of physicalnode mobility, a measure of topology change, and a measure of packetsloss within the reactive ad-hoc network.
 11. A method according to claim6, wherein the step of transmitting is performed absent at least one ofa predetermined known available route, establishing an availablecommunication path along a known route, maintaining the determined routeduring the communication, determining an approximately optimal route,and transmitting an acknowledgement message from the destination node tothe first node.
 12. A node forming part of a reactive ad-hoc networkcomprising: (a) a processor; (b) a memory in communication with theprocessor; (c) a transceiver in communication with the processor forreceiving signals and for transmitting signals, the signals transmittedand received via a wireless communication medium; and (d) an applicationin execution upon the processor executing an ad-hoc communicationsprotocol to communicate with at least one other node to form an ad-hocnetwork, the application: (i) at least one of generating, receiving fromthe transceiver and providing to the transceiver a packet of datacomprising message data and header data, the header data comprising datarelating to a source node and a destination node for the packet of data,data relating to a number of hops already completed for the packet ofdata, data relating to mobility of packets of data within the reactivead-hoc network transmitted from the source node to the destination nodeand the destination node to the source node, data relating to a numberof hops between the source node and the destination node for a previouspacket of data, and a unique identifier for the packet of data; (ii)calculating a discard counter, the discard counter being determined independence upon at least the direction of a received packet relative tothe source node and destination node, a packet mobility factor in thedirection of the packet, the number of hops from the source node to thesecond other node, the number of hops from the destination node to thesecond other node and the number of hops between the source node anddestination node for a previous packet of data; and (iii) determiningwhether to discard the packet in dependence upon at least the discardcounter and discarding the packet and decrementing the discard counterwhere the determination is made to discard.
 13. A node according toclaim 12 wherein the application in execution repeats (iii) forsubsequently received packets between the source node and destinationnode in the direction of the packet until either a subsequent packet isreceived in the reverse direction to the packet and the discard counteris recalculated or the discard counter becomes zero.
 14. A nodeaccording to claim 12 wherein the application in execution re-startsproviding packets of data to the transceiver when discard counterreduces to zero.
 15. A node according to claim 12 wherein theapplication establishes the data relating to mobility of packets of datain dependence upon at least one of a measure of physical node mobility,a measure of topology change, and a measure of packets loss within thereactive ad-hoc network.